Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1619

reference: 452-tree-1
name: 1619
tree-preservation-order: undefined
452-tpo-1
uprn
address-text
point: POINT (-1.038064 50.883224)
geometry: MULTIPOLYGON (((-1.038008 50.883218,-1.038010 50.883229,-1.038018 50.883239,-1.038030 50.883247,-1.038046 50.883253,-1.038064 50.883255,-1.038081 50.883253,-1.038097 50.883248,-1.038110 50.883240,-1.038118 50.883230,-1.038121 50.883219,-1.038119 50.883208,-1.038111 50.883198,-1.038098 50.883190,-1.038083 50.883185,-1.038065 50.883183,-1.038048 50.883184,-1.038032 50.883189,-1.038019 50.883197,-1.038011 50.883207,-1.038008 50.883218)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL